Post-Installation Checks and Tasks
The deployment playbooks have built-in post deployment checks to confirm that all components are started. However, this does not guarantee that application is in a normal state.
It is recommended that post deployment, you manually log into each of the applications that have a UI and confirm that it works as expected by performing a set of standard operations. If there are failures, check the logs as sometimes some of the services may need to be restarted.
CMP
Converged Monetisation Platform. The MDS Global product that supports customer care and billing for digital service providers. installs the following services:
| Component | Service Name |
|---|---|
| PostgreSQL | postgresql-16 |
| WSO2 Identity Server | wso2is |
| Role Extender | role-extender |
| JBoss / Wildfly | eap7-standalone |
| JWS / Tomcat | jws5-tomcat |
| Health Check Service | health-check |
| SAM Services | sam-services |
| Voucher Management Services | voucher-management-services |
| Shared Services | shared-services |
| REST Web Services | rest-ws |
| Bulk Action Console | bulk-action-console |
| Context Sensitive Help | context-sensitive-help |
| Artemis / ActiveMQ | artemis |
| SPaRC Engine | sparc-engine |
| SABRE Server | sabre-server |
| CMP Administration Console | sabre-console |
All CMP components are configured to start as systemd services. The standard systemctl command should be used to control the component services.
To check the status of a service - to see if you need to restart it, for example - run the following command:
sudo systemctl status <service_name>
To start a service, run the following command:
sudo systemctl start <service_name>
To stop the service, run the following command:
sudo systemctl stop <service_name>
And to restart the service, run the following command:
sudo systemctl restart <service_name>